This file supplements the information in the EnterNet Help utility. It contains helpful information that is either not documented elsewhere or requires emphasis. The following subjects are discussed:
This software will work on any Macintosh running Mac OS 7.6 or newer with Open Transport 1.1.2 or later. However, this software will not work with Mac OS X. Mac OS X users can use the PPPoE client software included with Mac OS X. (See your Mac OS X documentation for more information about this.)
During installation on PowerPC computers an Open Transport connection module named "ENI Network Access Module" will be installed in your Extensions folder. This module works with Apple's Remote Access software to provide PPPoE connections. Other software also is installed to help you create and manage your network connections.
If you are running a version of Mac OS older than 8.5 or a 68K-based Macintosh, "ENI Network Access Module" will not work with your computer. However, it still is installed so it will be available to you when you upgrade to a newer Mac OS. (You can safely remove the file if you do not plan to upgrade your Mac OS.)
Also during installation on computers running a version of Mac OS older than version 8.5, an mdev (MacTCP Device) named "EnterNet Classic" will be installed on the computer. This software works with the TCP/IP Control Panel to create a connection to the Internet. Please note that "EnterNet Classic" will stop working if you upgrade to a newer version of Open Transport after installing EnterNet. You can reactivate it by reinstalling EnterNet.
If you are installing the application from a CD, insert the CD into your drive, locate the file named "Install EnterNet" on the CD and double-click it. Follow the on-screen instructions.
If you downloaded the application from another computer, extract the file named "Install EnterNet" from the downloaded archive file and double click it. Follow the on-screen instructions.
You also can use the Custom Install option to install individual components such as "EnterNet Classic", "ENI Network Access Module", help files and others.
NOTE: Your Macintosh must be restarted after installing the System Folder items. The Installer will advise you of this and will perform the restart for you.
WARNING: Apple Location Manager Users
Installing EnterNet could cause you to lose some settings in your current location set. Please read the section "Using Location Manager" before installing EnterNet.
Whenever you restart, your Macintosh may ask you if you want to update the settings for your current location. This occurs because EnterNet installs new network configurations and makes them active. (See "About Network Configurations" for more information.) These new configurations are designed to enable your new software to connect quickly and automatically. To avoid altering your existing Location Manager settings, you should click Don't Update unless the specified location is the one you plan to use with EnterNet.
When installing EnterNet for the first time, after your computer restarts, use the Location Manager to create a new location for the current settings for TCP/IP and Remote Access. (These settings will have EnterNet in their names.) Then you can use the new location whenever you want to connect to the Internet using EnterNet.
Also note that the EnterNet Settings application and control strip module may automatically activate different configurations for the TCP/IP, Remote Access and Modem control panels. This may cause Location Manager to again ask to update the current location. You should choose Don't Update unless the specified location is the one you plan to use with EnterNet.
When installing EnterNet, the Installer will automatically create the network configurations necessary to connect to the Internet using EnterNet. When using EnterNet, the Settings application and control strip automatically may activate these network configurations.
To users unfamiliar with the Configurations menu item in the TCP/IP, Remote Access and Modem control panels, this looks like the software is replacing old network settings -- it is not. Instead, the old settings still are available using the Configurations item in the File menu of the appropriate network control panels. (If you never renamed the configurations, your original configurations will be named "Default".)
Furthermore, the configurations created by EnterNet have many of their settings locked. Locking these settings prevents novice users from accidentally changing them and thereby causing the network connection to stop working. If you want to change these settings, create a new configuration and change the settings in the new configuration.
If you are not familiar with Configurations in the network control panels, please review the Help documents available from the Help menu in each network control panel.
We know of several problems which might be important to you in EnterNet version 1.2.5:
- After installing EnterNet, Apple's Location Manager may ask if you want to update the settings for your current location. This occurs because the EnterNet installer has created new network configurations and made them active. See the section "Using Location Manager" for more information.
- Multi-processor systems using DAVE from Thursby Software <http://www.thursby.com/> and connecting with EnterNet RA may become unresponsive soon after the computer start up. This is caused by a conflict with the control strip module of DAVE version 2.5.2 and older. We have worked with Thursby Software to build a fix, which should be available in later versions of DAVE. Please contact Thursby Software for a newer version of DAVE if you encounter this problem. You also can avoid the problem by disabling the DAVE control strip module, or by deactivating the "Connect automatically when starting TCP/IP applications" option in the Remote Access control panel for the appropriate EnterNet RA configuration.
- Specifying a URL in the Preferences window for EnterNet RA configurations sometimes does not work. This happens when the URL is very long, or the configuration specifies a very long server or service name. For most users the best way around this problem is to not specify a server name in the Service Browser window. The total length of the service name, server name and the URL must be fewer than approximately 100 characters.
For the latest information about conflicts, incompatibilities and other issues related to EnterNet, review the EnterNet for Macintosh FAQ available from
- The Preferences window now works with EnterNet Classic connections. The configuration must be the active configuration (visible in the Settings window) when opening Preferences. These preference settings will apply to all EnterNet Classic connections. (EnterNet RA connections can have different preference settings for each configuration.)
- Choosing the option "Automatically connect on launch" will attempt to connect using the configuration displayed when the Settings application was closed.
- EnterNet now correctly converts EnterNet Classic configurations to EnterNet RA configurations when installing ENI Network Access Module. Previous versions incorrectly converted the named networks and did not work with non-English installations.
- EnterNet RA connections now work on NuBus PowerPC Macintosh computers. Earlier versions would connect but would not read large incoming packets such as Web pages.
- The ENI Network Access Module (used for EnterNet RA connections) was changed to more properly handle protocol timers. This change should have no visible affect.
- In prior versions the Settings application did not ask to save the configuration when changing the Connect Via option for EnterNet Classic configurations. This problem is fixed.
- EnterNet RA connections now report the secondary DNS information.
- The default MRU is changed to 1492 from 1454.
- Additional Settings application resources now are localizable.
- The Settings app Password field no longer supports Undo. This is necessary because the Settings app may not know what the password is on some versions of Mac OS.
- The Settings app now beeps and writes error information to the log when an unexpected failure occurs.
- The Settings application now automatically converts the last used EnterNet Classic configuration to an EnterNet RA configuration when it detects that it is running on a system recently upgraded to Mac OS 8.5 or later and there are no other EnterNet RA configurations.
Features & Fixes New in Version 1.2.4
---------------------------------
- EnterNet RA now works (again) with tunnelled networks which begin with CHAP authentication and use CHAP authentication on the second leg. (This failure was introduced in version 1.2.2.)
- EnterNet now correctly converts EnterNet Classic configurations to EnterNet RA configurations when installing ENI Network Access Module. Previous versions did not convert the password or properly support named networks.
- EnterNet RA configurations no longer negotiate MRU when using default settings. (This is to work around lame Cisco servers which are unable to properly negotiate MRU.) The default MTU remains 1454. These settings are configurable using the EnterNet Administration Kit.
Features & Fixes New in Version 1.2.3
---------------------------------
- Connections using EnterNet Classic now automatically disconnect when the computer is put to sleep. This should prevent the computer from crashing when being put to sleep with an open EnterNet Classic connection.
- The software now detects when it is running on a computer which is not capable of sleep. This should prevent crashes on older computers.
- The Installer now creates a valid Modem control panel configuration for use by EnterNet RA. Few users noticed this problem because the Settings application automatically fixed the invalid configuration with the first manual connection.
- The windows in the Settings application now use the application font specified by the OS instead of using Geneva. Earlier versions had problems properly displaying text in some languages.
- Network Name addressing (also known as Radius Realm addressing) now works properly with EnterNet RA connections. Prior versions corrupted the password when Network Name addressing was used.
- EnterNet RA did not properly configure the network settings on some installations of Mac OS 8.5 and 8.6. This occurs when there is no Modem Preferences file. The software now correctly configures the network settings on these older versions of Mac OS.
Features & Fixes New in Version 1.2.2
---------------------------------
- ENI Network Access Module can be configured to force PAP authentication.
- EnterNet RA now works with tunnelled networks which begin with CHAP authentication and then switch to PAP authentication on the second leg.
- Easy Install normally will install only EnterNet RA technology unless the computer is running a version of Mac OS older than Mac OS 8.6. EnterNet Classic is always available as a Custom Install option. Some ISPs may choose EnterNet Classic as the default configuration, in which case it will be installed as part of Easy Install in addition to EnterNet RA.
Features & Fixes New in Version 1.2.1
---------------------------------
- With prior versions the computer sometimes would not awaken from sleep if it had been put to sleep with an open EnterNet RA connection. This now is fixed.
- EnterNet occasionally was causing a crash during startup on some iBooks (dual-USB). This now is fixed.
- EnterNet RA can be configured to suppress outgoing LCP Echo Requests.
- EnterNet can be configured to use the default EnterNet Classic configuration when starting for the first time. Normally EnterNet will use the default EnterNet RA configuration when starting for the first time.
Features & Fixes New in Version 1.2
---------------------------------
- EnterNet now includes a native Open Transport PPPoE module (ENI Network Access Module) for communicating with the PPPoE server. (Requires Open Transport 2.0.3 from Mac OS 8.6.) This module uses Apple's Remote Access technology to automatically connect whenever an application attempts to use the TCP/IP network. PPPoE communications also are much faster.
- The Settings application automatically detects if the EnterNet Classic or EnterNet RA technology is in use and provides suitable controls for each.
- The Settings application can offer a choice of PPPoE services when used with the ENI Network Access Module.
- The EnterNet Classic networking module now reports server messages in the log. (Previously these messages were displayed in a modal alert.)
- The EnterNet Classic networking module now uses the DNS settings in the TCP/IP control panel when none are provided by the server.
- The EnterNet installer no longer removes TunnelBuilder modules from the System Folder. EnterNet and TunnelBuilder now should be able to coexist in the same system.
Should you find yourself in need of assistance with the application you should check the EnterNet Help utility before calling your support organization. The Help utility can be accessed either by selecting "Open EnterNet Help" from the application's Help menu, or it can be accessed directly. To access the Help utility without launching the application, double-click the file named "User's Guide.html" in the "EnterNet" folder. This will display the help information in your chosen browser.
EnterNet is purchased by ISPs and other companies to enable their end-user customers or employees to access the Internet or to access their private intranets and extranets. Should the application's Help utility not provide the assistance you need, you should contact the organization from which you acquired it. Efficient Networks does not provide technical assistance directly to end users.
